Determining proximity of user equipment for device-to-device communication

ABSTRACT

Embodiments of apparatus, packages, computer-implemented methods, systems, devices, and computer-readable media (transitory and non-transitory) are described herein for ascertaining, e.g., by a traffic detection function (“TDF”), that a first user equipment (“UE”) and a second UE are, potentially, sufficiently proximate to each other to wirelessly exchange data directly. In various embodiments, an evolved serving mobile location center (“E-SMLC”) may be instructed, e.g., by the TDF, to obtain location change data associated with the first and second UEs. In various embodiments, a determination may be made, e.g., by the TDF, based on the location change data, whether the first and second UEs are sufficiently proximate to exchange data directly, and whether the first and second UEs are likely to remain proximate for at least a predetermined time interval. In various embodiments, the first and second UEs may be caused to commence device-to-device (“D 2 D”) communication based on the determination.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/525,100 entitled “DETERMINING PROXIMITY OF USER EQUIPMENT FORDEVICE-TO-DEVICE COMMUNICATION,” filed Oct. 27, 2014, which is acontinuation of U.S. patent application Ser. No. 13/681,361 entitled“DETERMINING PROXIMITY OF USER EQUIPMENT FOR DEVICE-TO-DEVICECOMMUNICATION,” filed Nov. 19, 2012 2012 and issued as U.S. Pat. No.8,874,103 on Oct. 28, 2014, which claims priority to U.S. ProvisionalPatent Application No. 61/646,223 entitled “ADVANCED WIRELESSCOMMUNICATION SYSTEMS AND TECHNIQUES,” filed May 11, 2012. Alldisclosures of which are incorporated herein by their references.

FIELD

Embodiments of the present invention relate generally to the technicalfield of data processing, and more particularly, to determiningproximity of user equipment (“UE”) for device-to-device (“D2D”)communication.

BACKGROUND

The background description provided herein is for the purpose ofgenerally presenting the context of the disclosure. Work of thepresently named inventors, to the extent it is described in thisbackground section, as well as aspects of the description that may nototherwise qualify as prior art at the time of filing, are neitherexpressly nor impliedly admitted as prior art against the presentdisclosure. Unless otherwise indicated herein, the approaches describedin this section are not prior art to the claims in the presentdisclosure and are not admitted to be prior art by inclusion in thissection.

Wireless mobile devices (e.g., user equipment, or “UE”) may communicatewith each other over a wireless wide area network (“WWAN”), e.g., usingradio access technologies (“RAT”) such as the 3GPP Long Term Evolution(“LTE”) Advanced Release 10 (March 2011) (the “LTE-A Standard”), theIEEE 802.16 standard, IEEE Std. 802.16-2009, published May 29, 2009(“WiMAX”), as well as any other wireless protocols that are designatedas 3G, 4G, 5G, and beyond.

Some UEs also may be configured to communicate directly with other UEs,e.g., using device-to-device (“D2D”) communication. D2D communicationmay be used, e.g., when UEs initiate communication with each other whilewithin direct wireless range of each other. RATs that may be used inthis manner may include 802.11 (“WiFi”), BlueTooth, near fieldcommunication (“NFC”), FlashLinq by Qualcomm®, and so forth.

UEs may initiate communication with each other over a WWAN, but may bein, or move into, sufficient proximity to exchange data directly, e.g.,using WiFi Direct, BlueTooth, Flashlinq, NFC, etc. Continuing to usingWWAN resources to communicate in such a situation may drain WWANresources that may be put to better use for communications between UEsthat are remote from each other.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example and not by wayof limitation in the figures of the accompanying drawings.

FIG. 1 schematically illustrates various network entities configuredwith applicable portions of the present disclosure to facilitatecommencement of device-to-device (“D2D”) communication between userequipment (“UE”), in accordance with various embodiments of the presentdisclosure.

FIG. 2 schematically depicts an example of communications that may beexchanged between various network entities configured with applicableportions of the teachings of the present disclosure, in accordance withvarious embodiments of the present disclosure.

FIG. 3 schematically depicts an example method that may be implementedby a traffic detection function (“TDF”), in accordance with variousembodiments of the present disclosure.

FIG. 4 schematically depicts an example method that may be implementedby an evolved serving mobile location center (“E-SMLC”), in accordancewith various embodiments.

FIG. 5 schematically depicts an example of communications, similar tothose shown in FIG. 2, that may be exchanged between various networkentities configured with applicable portions of the teachings of thepresent disclosure, in accordance with various embodiments of thepresent disclosure.

FIG. 6 schematically depicts an example method that may be implementedby an evolved Node B (“eNB”), in accordance with various embodiments.

FIG. 7 schematically depicts an example method that may be implementedby a UE, in accordance with various embodiments.

FIG. 8 schematically depicts an example computing device on whichdisclosed methods and computer-readable media may be implemented, inaccordance with various embodiments.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings which form a part hereof wherein like numeralsdesignate like parts throughout, and in which is shown by way ofillustration embodiments that may be practiced. It is to be understoodthat other embodiments may be utilized and structural or logical changesmay be made without departing from the scope of the present disclosure.Therefore, the following detailed description is not to be taken in alimiting sense, and the scope of embodiments is defined by the appendedclaims and their equivalents.

Various operations may be described as multiple discrete actions oroperations in turn, in a manner that is most helpful in understandingthe claimed subject matter. However, the order of description should notbe construed as to imply that these operations are necessarily orderdependent. In particular, these operations may not be performed in theorder of presentation. Operations described may be performed in adifferent order than the described embodiment. Various additionaloperations may be performed and/or described operations may be omittedin additional embodiments.

For the purposes of the present disclosure, the phrases “A or B” and “Aand/or B” mean (A), (B), or (A and B). For the purposes of the presentdisclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B),(A and C), (B and C), or (A, B and C).

The description may use the phrases “in an embodiment,” or “inembodiments,” which may each refer to one or more of the same ordifferent embodiments. Furthermore, the terms “comprising,” “including,”“having,” and the like, as used with respect to embodiments of thepresent disclosure, are synonymous.

As used herein, the terms “module” and/or “logic” may refer to, be partof, or include an Application Specific Integrated Circuit (“ASIC”), anelectronic circuit, a processor (shared, dedicated, or group) and/ormemory (shared, dedicated, or group) that execute one or more softwareor firmware programs, a combinational logic circuit, and/or othersuitable components that provide the described functionality.

An example wireless wide area network (“WWAN”) 100 is depicted inFIG. 1. A first mobile device in the form of a first user equipment(“UE”) 102 (configured with applicable portions of the teachings of thepresent disclosure) and a second mobile device in the form of a secondUE 104 (configured with applicable portions of the teachings of thepresent disclosure) may be in wireless communication with each other viaWWAN 100. In particular, first UE 102 and second UE 104 may be in directcommunication with a radio access network (“RAN”) via an access point inthe form of an evolved Node B (“eNB”) 106.

Although first UE 102 is depicted as a touch screen smart phone, andsecond UE 104 is depicted as a laptop computer, this is not meant to belimiting. As discussed below, mobile devices (e.g., UEs) describedherein may be any type of data processing device, including but notlimited to a tablet computer, a personal digital assistant (“PDA”), aportable gaming device, and so forth.

eNB 106 may be in network communication with various components of anEvolved Packet Core (“EPC”). For example, eNB 106 may be in networkcommunication with a mobility management entity (“MME”) 108. MME 108 maybe configured to perform various functions, including but not limited tonon-access stratum (“NAS”) signaling and NAS signaling security, idlemode UE reachability, public data network (“PDN”) and serving gatewayselection, MME selection for handoffs, authentication, bearer managementfunctions, and so forth.

MME 108 may itself be in network communication with various other nodes.For instance, MME 108 may be in network communication with an evolvedserving mobile location center (“E-SMLC”) 110. E-SMLC 110 may beconfigured to perform various functions related to location services(“LCS”). For example, E-SMLC 110 may manage the support of differentlocation services for target UEs, e.g., including positioning of UEs anddelivery of assistance data to UEs. In various embodiments, E-SMLC 110may interact with the serving eNB (e.g., 106) for a target UE (e.g.,102, 104) in order to obtain position measurements for the target UE.These position measurements may include but are not limited to uplinkmeasurements made by the serving eNB and downlink measurements made bythe target UE. The downlink measurements may have been provided to theserving eNB as part of other functions, such as support of handover.E-SMLC 110 may interact with a target UE (e.g., 102, 104) in order todeliver assistance data if requested for a particular location service,or to obtain a location estimate if that was requested. In variousembodiments, in addition to or instead of E-SMLC 110, a gateway mobilelocation center (“G-MLC”) 111 may perform similar functions as E-SMLC110.

For positioning of a target UE (e.g., 102, 104), E-SMLC 110 (or G-MLC111) may determine the positioning method to be used, based on factorssuch as LCS client type, a required quality of service (“QoS”), UEpositioning capabilities, and/or eNB positioning capabilities. E-SMLC110 may invoke these positioning methods in the target UE and/or servingeNB. UE-based positioning methods may yield a location estimate.UE-assisted and network-based positioning methods may yield positioningmeasurements. E-SMLC 110 may combine received results and, based onthose results, determine a single location estimate for the target UE,as well as other information such as an accuracy of the estimate.

E-SMLC 110 (or G-MLC 111) may be in network communication with variousother network entities. For instance, E-SMLC 110 may be in networkcommunication with a traffic detection function (“TDF”) 112. While TDF112 is depicted in FIG. 1 as operating on a separate server computer,this is not meant to be limiting. TDF 112 may be implemented using anycombination of hardware and software on any network computing device,such as those shown in FIG. 1 and others that are not shown but areoften found in wireless communication networks. Moreover, in variousembodiments, one or more of the entities depicted in FIG. 1 may beimplemented on the same or different computing devices.

In various embodiments, if first UE 102 and second UE 104 aresufficiently proximate, and assuming both first UE 102 and second UE 104are equipped with the same direct radio access technology (“RAT”), e.g.,WiFi Direct, Bluetooth, near field communication (“NFC”), Flashlinq,etc. then first UE device 102 and second UE device 104 may be able toexchange data directly. For example, in FIG. 1, assume first UE 102 andsecond UE 104 are in communication already via WWAN 100 and areseparated by a distance D. If D is less than a particular threshold,such as a maximum range of a particular RAT, then first UE 102 andsecond UE 104 may be able to communicate directly, e.g., usingdevice-to-device (“D2D”) communication, rather than through WWAN 100.

However, while first UE 102 and second UE 104 may momentarily be withinsufficient proximity to commence D2D communication, they might notnecessarily remain in sufficient proximity for long enough to justify atransition to D2D communication. For instance, a user of first UE 102may be moving in one direction, and a user of second UE 104 may bemoving in a different direction. The WWAN resources gained by commencingD2D communication between first UE 102 and second UE 104 may not beworth the network resources expended to implement the transition if theD2D communication will be short-lived.

Accordingly, in various embodiments, various network entities may beconfigured to determine not only whether first UE 102 and second UE 104are sufficiently proximate to exchange data directly, but also whetherthey will remain proximate for an amount of time that justifiescommencing D2D communication between the UEs.

In various embodiments, TDF 112 may be configured to ascertain thatfirst UE 102 and second UE 104 are, potentially, sufficiently proximateto each other to wirelessly exchange data directly. Various events maycause TDF 112 to make this ascertainment. As one non-limiting example,eNB 106 may determine that it is serving both first UE 102 and second UE104. In such case, eNB 106 may be configured to transmit a request(e.g., an LCS request) to TDF 112 to determine whether first UE 102 andsecond UE 104 are sufficiently proximate to exchange data directly,e.g., using D2D communication. As another non-limiting example, first UE102 or second UE 104 may itself determine that there is a possibilitythat the other is, potentially, sufficiently proximate to commence D2Dcommunication. In such case, the UE device may transmit a request (e.g.,an LCS request) to TDF 112 to determine whether first UE 102 and secondUE 104 are sufficiently proximate to exchange data directly.

Upon ascertaining that first UE 102 and second UE 104 are, potentially,sufficiently proximate to exchange data directly, TDF 112 may instructE-SMLC 110 (or G-MLC 111) to obtain location change data associated withthe first UE 102 and/or second UE 104. As used herein, the term“location change data” may include any data that demonstrates a changeof location of a UE. For instance, location change data may include avelocity of a UE. Being a vector, a UE velocity may include a both speedcomponent and a direction component. For instance, if the distance Dbetween first UE 102 and second UE is growing at a particular rate overtime, that may indicate that first UE 102 and second UE 104 are movingaway from each other. Location change data may include any otherindications of movement of UEs, such as acceleration.

In some embodiments, TDF 112 may instruct E-SMLC 110 (or G-MLC 111) toobtain location change data associated with one or more UEs via a directsignaling interface. In other embodiments, such as the example shown inFIG. 2, this may be done through other nodes. Referring now to FIG. 2,at arrow 220, TDF 112 may send a request for location change informationassociated with the first UE 102 and/or second UE 104 to MME 108. Atarrow 222, MME 108 may forward this request to E-SMLC 112 (or G-MLC111). In other embodiments, TDF 112 may transmit this instruction viaother nodes. For example, TDF 112 may transmit the instruction to E-SMLC110 (or G-MLC 111) through MME 108, e.g., using a logical tunnel.

At arrow 224, E-SMLC 110 (or G-MLC 111) may instigate locationprocedures with serving eNB 106. For example, E-SMLC 110 (or G-MLC 111)may request that eNB 108 provide location change data associated withfirst UE 102 and/or second UE 104. In various embodiments, E-SMLC 110(or G-MLC 111) may also obtain assistance data from eNB 106, forprovision to a target UE such as 102 or 104.

Additionally or alternatively to arrow 224, at arrow 226, E-SMLC 110 (orG-MLC 111) may instigate location procedures with UE 102 or 104. Invarious embodiments, E-SMLC 110 (or G-MLC 111) may obtain a locationestimate (e.g., a GPS coordinate) or location change data from UE 102 or104. In various embodiments, E-SMLC 110 (or G-MLC 111) may transfer, toUE 102 or 104, the assistance data obtained from eNB 106 at block 224.This assistance data may be used to assist with UE-based and/orUE-assisted positioning methods. At arrow 228, UE 102 or 104 maytransmit location change data associated with first UE 102 or second UE104 to E-SMLC 110 (or G-MLC 111), e.g., through eNB 106 and/or MME 108.

Upon receiving location change data associated with first UE 102 and/orsecond UE 104, E-SMLC 110 (or G-MLC 111) may provide the location changedata to TDF. In some embodiments, e.g., where TDF 112 and E-SMLC 110 (orG-MLC 111) establish a direct signaling interface, this communicationmay be sent directly. In other embodiments, such as the one depicted inFIG. 2, at arrow 230, E-SMLC 110 (or G-MLC 111) may forward the locationchange data to MME 108. MME 108 may in turn forward the location changedata to TDF 112 at arrow 232.

Once it receives the location change data, TDF 112 may determine, basedon the location change data, whether first UE 102 and second UE 104 aresufficiently proximate to exchange data directly, and whether they arelikely to remain proximate for at least a predetermined time interval.In various embodiments, the predetermined time interval may be selectedto be long enough so that the benefits of commencing D2D communication(e.g., reduced WWAN network traffic) outweigh the costs of thetransition. This predetermined time interval may be set, e.g., by anetwork administrator, or may be dynamic, e.g., based on current networktraffic. In various embodiments, the determination as to whether the UEswill remain proximate for a sufficient time may be made based on variouslaws of physics and motion. For instance, relative velocities and/oraccelerations of two UEs reveal, e.g., as input in standardphysics/motion equations, that the UEs will be within direct wirelessrange for a sufficient amount of time to justify commencement of D2Dcommunication.

If TDF 112 determines that first UE 102 and second UE 104 will be inproximity for at least the predetermined time interval, TDF 112 maycause first UE 102 and second UE 104 to commence D2D communication. Forexample, in various embodiments, TDF 112 may instruct MME 108 to causefirst UE 102 and second UE 104 to commence D2D communication. In variousembodiments, MME 108 may utilize NAS signaling to instruct first UE 102and second UE 104 to commence D2D communication.

FIG. 3 depicts an example method 300 that may be implemented by acomputing device as part of operating a TDF such as TDF 112. At block302, TDF 112 may await a request to instigate and/or perform locationservices. At block 304, TDF 112 may receive, from various network nodes,a request to determine whether two or more UEs , e.g., first UE 102 andsecond UE 104, exchanging data indirectly through a WWAN are insufficient proximity to exchange data directly, e.g., using D2Dcommunication. The request may also seek to have TDF 112 determinewhether the first and second UEs will be proximate for a sufficientamount of time, such as a predetermined time interval, to warrantcommencement of D2D communication.

At 306, TDF 112 may instruct an E-SMLC or G-MLC, e.g., E-SMLC 110, toobtain location change data associated with the first and second UEs(e.g., 102 and 104). In some embodiments, TDF 112 may have a directsignaling interface with E-SMLC 110, and therefore may transmit thisinstruction directly, e.g., bypassing MME 108. In other embodiments, TDF112 may transmit this instruction to MME 108, which in turn may forwardthe instruction to E-SMLC 110. At block 308, TDF 112 may receivelocation change data, e.g., from E-SMLC 110 by way of MME 108.

At block 310, TDF 112 may determine, based on the received locationchange data, whether the first and second UEs are sufficiently proximateto exchange data directly. If the answer is yes, then at block 312, TDF112 may determine whether the first and second UEs are likely to remainproximate for at least a predetermined time interval (e.g., based onstandard laws of physics/motion). If the answer is yes, then at block314, TDF 112 may cause first UE 102 and second UE 104 to commence D2Dcommunication. If the answer at either block 310 or block 312 is no,then method 300 may proceed back to block 302.

FIG. 4 depicts an example method 400 that may be implemented by, e.g.,E-SMLC 110 or G-MLC 111, in accordance with various embodiments. Atblock 402, E-SMLC 110/G-MLC 111 may receive, e.g., from TDF 112, arequest for location change data associated with first UE 102 or secondUE 104. At block 404, E-SMLC 110/G-MLC 111 may request, e.g., from firstUE 102, second UE 104, or eNB106 serving first UE 102 or second UE 104,the location change data. At block 406, E-SMLC 110/G-MLC 111 maytransmit the location change data, e.g., to TDF 112.

FIG. 5 depicts a slight variation of the data exchange shown in FIG. 2.In this example, arrows 520, 522 524, 530 and 532 represent dataexchanges similar to those represented by arrows 220, 222, 224, 230 and232 in FIG. 2, respectively. However, FIG. 5 differs from FIG. 2 atarrows 526 and 528. Rather than E-SMLC 110 (or G-MLC 111) instigatinglocation procedures with UE 102 or 104, at arrow 626, eNB 106 mayinstigate (e.g., at the request of E-SMLC 110) location procedures withUE 102 or 104. For example, eNB 106 may encapsulate a request forlocation services in an radio resource control (“RRC”) and/or NAS signalto UE 102 or UE 104. UE 102 or 104 may encapsulate a response in an RRCand/or NAS signal back to eNB 106. eNB 106 may then forward the UElocation data to E-SMLC 110 at arrow 528.

FIG. 6 depicts an example method 600 that may be implemented by, e.g.,eNB 106, to exchange communications as shown in FIG. 5. At block 602,eNB 106 may receive, e.g., from E-SMLC 110 (or G-MLC 111), a request forlocation change data associated with first UE 102 or a second UE 104. Atblock 604, eNB 106 may obtain, e.g., from first UE 102 or second UE 104,e.g., on a control plane over an air interface using RRC and/or NASsignaling, the location change data. For example, eNB 106 mayencapsulate a location message (e.g., a request) into an RRC and/or NASmessage and send it first UE 102 using RRC. First UE 102 may decapsulatethe RRC and/or NAS message and consume the contents (e.g., the request).First UE 102 may likewise encapsulate location change data into a returnRRC and/or NAS message, and send it back to eNB 106 using RRC and/or NASsignaling. At block 606, eNB 106 may decapsulate the message and providethe contents, e.g., the location change data, to E-SMLC 110 (or G-MLC111).

FIG. 7 depicts an example method 700 that may be implemented by, e.g.,first UE 102 or second UE 104. At block 702, a UE (e.g., first UE 102)may receive, from an eNB (e.g., eNB 106) serving the UE, on a controlplane using at least one of RRC and NAS signaling, a request forlocation change data. At block 704, the UE may provide, to the eNB on acontrol plane using at least one of RRC and NAS signaling, the locationchange data. At block 706, the UE may receive, e.g., from a TDF (e.g.,TDF 112), a command to commence D2D communication with another UE (e.g.,second UE 104) served by the eNB, e.g., upon the TDF determining thatthe UE and the another UE are sufficiently proximate to exchange datadirectly and are likely to remain proximate for at least a predeterminedtime interval. At block 708, the UE may commence D2D with the another UEserved by the eNB

FIG. 8 illustrates an example computing device 800, in accordance withvarious embodiments. UE (e.g., 102, 104) or another network entity(e.g., 108, 110, 112) as described herein may be implemented on acomputing device such as computing device 800. Computing device 800 mayinclude a number of components, one or more processor(s) 804 and atleast one communication chip 806. In various embodiments, the one ormore processor(s) 804 each may be a processor core. In variousembodiments, the at least one communication chip 806 may also bephysically and electrically coupled to the one or more processors 804.In further implementations, the communication chip 806 may be part ofthe one or more processors 804. In various embodiments, computing device800 may include printed circuit board (“PCB”) 802. For theseembodiments, the one or more processors 804 and communication chip 806may be disposed thereon. In alternate embodiments, the variouscomponents may be coupled without the employment of PCB 802.

Depending on its applications, computing device 800 may include othercomponents that may or may not be physically and electrically coupled tothe PCB 802. These other components include, but are not limited to,volatile memory (e.g., dynamic random access memory 808, also referredto as “DRAM”), non-volatile memory (e.g., read only memory 810, alsoreferred to as “ROM”), flash memory 812, an input/output controller 814,a digital signal processor (not shown), a crypto processor (not shown),a graphics processor 816, one or more antenna 818, a display (notshown), a touch screen display 820, a touch screen controller 822, abattery 824, an audio codec (not shown), a video codec (not shown), aglobal positioning system (“GPS”) device 828, a compass 830, anaccelerometer (not shown), a gyroscope (not shown), a speaker 832, acamera 834, and a mass storage device (such as hard disk drive, a solidstate drive, compact disk (“CD”), digital versatile disk (“DVD”))(notshown), and so forth. In various embodiments, the processor 804 may beintegrated on the same die with other components to form a System onChip (“SoC”).

In various embodiments, volatile memory (e.g., DRAM 808), non-volatilememory (e.g., ROM 810), flash memory 812, and the mass storage devicemay include programming instructions configured to enable computingdevice 800, in response to execution by one or more processors 804, topractice all or selected aspects of methods 300, 400, 600 or 700,depending on whether computing device 800 is used to implement first UE102, second UE 104, TDF 112, eNB 106, E-SMLC 110, or G-MLC 111. Morespecifically, one or more of the memory components such as volatilememory (e.g., DRAM 808), non-volatile memory (e.g., ROM 810), flashmemory 812, and the mass storage device may include temporal and/orpersistent copies of instructions that, when executed, by one or moreprocessors 804, enable computing device 800 to operate one or moremodules 836 configured to practice all or selected aspects of methods300, 400, 600 or 700, depending on whether computing device 800 is usedto implement first UE 102, second UE 104, TDF 112, eNB 106, E-SMLC 110,or G-MLC 111.

The communication chips 806 may enable wired and/or wirelesscommunications for the transfer of data to and from the computing device800. The term “wireless” and its derivatives may be used to describecircuits, devices, systems, methods, techniques, communicationschannels, etc., that may communicate data through the use of modulatedelectromagnetic radiation through a non-solid medium. The term does notimply that the associated devices do not contain any wires, although insome embodiments they might not. The communication chip 806 mayimplement any of a number of wireless standards or protocols, includingbut not limited to IEEE 802.20, General Packet Radio Service (“GPRS”),Evolution Data Optimized (“Ev-DO”), Evolved High Speed Packet Access(“HSPA+”), Evolved High Speed Downlink Packet Access (“HSDPA+”), EvolvedHigh Speed Uplink Packet Access (“HSUPA+”), Global System for MobileCommunications (“GSM”), Enhanced Data rates for GSM Evolution (“EDGE”),Code Division Multiple Access (“CDMA”), Time Division Multiple Access(“TDMA”), Digital Enhanced Cordless Telecommunications (“DECT”),Bluetooth, derivatives thereof, as well as any other wireless protocolsthat are designated as 3G, 4G, 5G, and beyond. The computing device 800may include a plurality of communication chips 806. For instance, afirst communication chip 806 may be dedicated to shorter range wirelesscommunications such as Wi-Fi and Bluetooth and a second communicationchip 806 may be dedicated to longer range wireless communications suchas GPS, EDGE, GPRS, CDMA, WiMAX, LTE, Ev-DO, and others.

In various implementations, the computing device 800 may be a laptop, anetbook, a notebook, an ultrabook, a smart phone, a computing tablet, apersonal digital assistant (“PDA”), an ultra mobile PC, a mobile phone,a desktop computer, a server, a printer, a scanner, a monitor, a set-topbox, an entertainment control unit (e.g., a gaming console), a digitalcamera, a portable music player, or a digital video recorder. In furtherimplementations, the computing device 800 may be any other electronicdevice that processes data.

Embodiments of apparatus, packages, computer-implemented methods,systems, devices, and computer-readable media (transitory andnon-transitory) are described herein for a TDF configured to ascertainthat a first UE and a second UE are, potentially, sufficiently proximateto each other to wirelessly exchange data directly. In variousembodiments, the TDF may instruct an E-SMLC to obtain location changedata associated with the first and second UEs. In various embodiments,the TDF may determine, based on the location change data, whether thefirst and second UEs are sufficiently proximate to exchange datadirectly, and whether the first and second UEs are likely to remainproximate for at least a predetermined time interval. In variousembodiments, the TDF may cause the first and second UEs to commence D2Dcommunication based on the determination.

In various embodiments, the location change data may include informationabout a velocity and/or acceleration of the first or second UE. Invarious embodiments, the location change data may include comprisesinformation about a rate of change of relative locations of the firstand second UEs.

In various embodiments, the TDF may instruct the E-SMLC to obtain thelocation change data via at least one of RRC or NAS signaling over acontrol plane of a RAN. In various embodiments, the TDF may instruct anMME to cause the first and second UEs to commence D2D communication. Invarious embodiments, the TDF may instruct the MME to use NAS signalingto instruct the first and second UEs to commence D2D communication. Invarious embodiments, the TDF may instruct the E-SMLC using a directsignaling interface.

In various embodiments, the TDF may ascertain that the first and secondUEs are, potentially, sufficiently proximate to each other to wirelesslyexchange data directly based on a request from the first or second UE.In various embodiments, the TDF may ascertain that the first and secondUEs are, potentially, sufficiently proximate to each other to wirelesslyexchange data directly based on a request for location services from aneNB in communication with and/or serving the first or second UE.

In various embodiments, an eNB may be configured to obtain, from anE-SMLC, a request for location change data associated with a first UE ora second UE. In various embodiments, the eNB may obtain, from the firstor second UE using RRC and/or NAS signaling, the location change data.In various embodiments, the eNB may provide the location change data tothe E-SMLC. In various embodiments, receipt of the request for locationchange data and provision of the location change data are direct to theE-SMLC, bypassing a MME.

In various embodiments, a system may include one or more processors,memory operably coupled to the one or more processors, and instructionsin the memory that, when executed by the one or more processors, causethe one or more processors to operate an E-SMLC. In various embodiments,the E-SMLC may be configured to receive, from a TDF, a request forlocation change data associated with a first UE or a second UE. Invarious embodiments, the E-SMLC may be configured to request, from thefirst UE, the second UE, or an eNB serving the first or second UE, thelocation change data. In various embodiments, the E-SMLC may beconfigured to transmit the location change data to the TDF. In variousembodiments, the location change data may include information about avelocity of the first or second UE. In various embodiments, the E-SMLCmay be further configured to cause the eNB to obtain the location changedata from the first or second UE using radio resource control signaling.In various embodiments, the E-SMLC may be configured to receive therequest from the TDF via an MME. In various embodiments, the E-SMLC maybe configured to receive the request directly from the TDF, bypassing anMME. In various embodiments, the E-SMLC may include a Bluetoothtransceiver.

In various embodiments, a UE may include processing circuitry toreceive, from an eNB serving the UE, using at least one of RRC and NASsignaling, a request for location change data. In various embodiments,the processing circuitry may be configured to provide, to the eNB usingat least one of RRC and NAS signaling, the location change data. Invarious embodiments, the processing circuitry may be configured tocommence D2D communication with another UE served by the eNB responsiveto a determination that the UE and the another UE are sufficientlyproximate to exchange data directly and are likely to remain proximatefor at least a predetermined time interval. In various embodiments, theprocessing circuitry may be configured to commence the D2D communicationwith the another UE responsive to a command from a TDF.

Although certain embodiments have been illustrated and described hereinfor purposes of description, this application is intended to cover anyadaptations or variations of the embodiments discussed herein.Therefore, it is manifestly intended that embodiments described hereinbe limited only by the claims.

Where the disclosure recites “a” or “a first” element or the equivalentthereof, such disclosure includes one or more such elements, neitherrequiring nor excluding two or more such elements. Further, ordinalindicators (e.g., first, second or third) for identified elements areused to distinguish between the elements, and do not indicate or imply arequired or limited number of such elements, nor do they indicate aparticular position or order of such elements unless otherwisespecifically stated.

What is claimed is:
 1. An apparatus to be included in a network entity, the apparatus comprising: receiver circuitry to receive information associated with a location change over time for at least one of a first user equipment (“UE”) or a second UE; processing circuitry, coupled with the receiver circuitry, to determine that the first UE and the second UE are to be proximate with one another for a predetermined period of time based on the received information; and transmitter circuitry, coupled with the processing circuitry, to transmit, based on the determination that the first UE and the second UE are to be proximate with one another for the predetermined period of time, an instruction to cause the first UE and the second UE to establish a direct wireless connection with one another.
 2. The apparatus of claim 1, wherein the information associated with the location change over time comprises at least one of a velocity of the first or second UE, an acceleration of the first or second UE, or a rate of change of relative locations of the first and second UEs.
 3. The apparatus of claim 1, wherein the receiver circuitry is to receive a first location associated with the first UE and a second location associated with the second UE, and further wherein the determination, by the processing circuitry, that the first UE and the second UE are to be proximate with one another is based on the first and second locations.
 4. The apparatus of claim 1, wherein the transmitter circuitry is to transmit an instruction to an evolved serving mobile location center (“E-SMLC”) to obtain the information associated with the location change over time.
 5. The apparatus of claim 4, wherein the instruction to the E-SMLC indicates use of one of radio resource control (“RRC”) or non-access stratum (“NAS”) signaling over a control plane of a radio access network (“RAN”).
 6. The apparatus of claim 1, wherein the transmitter circuitry is to transmit the instruction to a mobility management entity (“MME”).
 7. The apparatus of claim 1, wherein the receiver circuity is to receive a request associated with the first UE or the second UE, and further wherein the determination, by the processing circuitry, that the first UE and the second UE are to be proximate with one another is based on the request.
 8. The apparatus of claim 7, wherein the request comprises a request for location services from an evolved Node B (“eNB”) that is to serve at least one of the first or the second UEs.
 9. A method to be performed by a traffic detection function (“TDF”), the method comprising: instructing an evolved serving mobile location center (“E-SMLC”) to obtain information associated with a location change over time associated with at least one of a first user equipment (“UE”) or a second UE; determining, based on the information associated with a location change over time, that the first UE and the second UE are to be proximate with one another for a predetermined period of time; and transmitting an instruction that is to cause the first and second UEs to establish a direct wireless connection based on the determining.
 10. The method of claim 9, wherein the information associated with the location change over time comprises at least one of a velocity of the first or second UE, an acceleration of the first or second UE, or a rate of change of relative locations of the first and second UEs.
 11. The method of claim 9, wherein the instructing of the E-SMLC to obtain the information associated with the location change over time includes an indication of whether to use radio resource control (“RRC”) or non-access stratum (“NAS”) signaling over a control plane of a radio access network (“RAN”).
 12. The method of claim 9, further comprising: instructing a mobility management entity (“MME”) to cause the first and second UEs to establish the direct wireless connection.
 13. The method of claim 9, further comprising: receiving a request associated with the first UE or the second UE; determining that the first UE and the second UE are to be proximate with one another based on the request.
 14. The apparatus of claim 13, wherein the request comprises a request for location services from an evolved Node B (“eNB”) that is to serve at least one of the first or the second UEs.
 15. Evolved Node B (“eNB”) circuitry comprising: receiver circuitry to receive, from an evolved mobile location center (“E-SMLC”), a first request for information associated with the location change over time and to receive location information from a first UE based on a second request; transmitter circuitry to transmit the second request to the first UE using radio resource control (“RRC”) or non-access stratum (“NAS”) signaling and to transmit the information associated with the location change over time to the E-SMLC based on the first request; and processing circuitry, coupled with the receiver circuitry and the transmitter circuitry, to serve the first UE and to determine the information associated with the location change over time based on the location information received from the first UE.
 16. The eNB circuitry of claim 15, wherein the information associated with the location change over time comprises at least one of a velocity of the first UE, an acceleration of the first UE, or a rate of change of relative locations of the first UE to a second UE that is also served by the eNB circuitry.
 17. The eNB circuitry of claim 15, wherein the request for the information associated with the location change over time is received directly from the E-SMLC and not from a mobility management entity (“MME”). 